On 3/4/24 11:09, Hans Hagen via ntg-context wrote:
> [...]
> in luametatex we have a bit more advanced mechanism (also relates to
> compact mode) because th eengine is a bit more clever
>
> just make sure that you don't add up features where one calcels the
> other, so use for instance:
Many
On 3/3/2024 11:54 AM, Pablo Rodriguez via ntg-context wrote:
Dear list,
I have the following sample:
\definefontfeature[wider][extend=2]
\definefontfamily[mainface][rm][TeX Gyre Pagella]
[features={default, quality, wider},
it={style: regular, features:{default, slanted,
Dear list,
I have the following sample:
\definefontfeature[wider][extend=2]
\definefontfamily[mainface][rm][TeX Gyre Pagella]
[features={default, quality, wider},
it={style: regular, features:{default, slanted, quality}},
bf={style: regular, features:{default, boldened-30}},
On 9/2/23 12:42, Wolfgang Schuster wrote:
> Pablo Rodriguez schrieb am 02.09.2023 um 12:35:
>> [...]
>> Sorry, but I don‘t know why this doesn‘t get the slanted font as bold (I
>> know I should know better, but I‘m stuck at this):
>>
>> \definefontfamily[mainface][rm][DejaVu Sans]
>>
Pablo Rodriguez schrieb am 02.09.2023 um 12:35:
[...]
Sorry, but I don‘t know why this doesn‘t get the slanted font as bold (I
know I should know better, but I‘m stuck at this):
\definefontfamily[mainface][rm][DejaVu Sans]
[sl≃style:bf]
You're using the wrong symbol (you have a math
On 9/2/23 12:18, Wolfgang Schuster wrote:
> Hans Hagen schrieb am 02.09.2023 um 11:53:
> [...]
>> in lpdf-lmt.lmt you can try:
>>
>> l 593
>>
>> tmsy = tmsy * sc
>>
>> l 610
>>
>> tmsy = tmsy * f_y_scale
>
> I get now with LMTX the
higher font size gives less slanted text (or not at all).
Using MkIV text is slanted fine, independent from font size.
Could anyone confirm the issue?
I can confirm the slant decreases at larger font sizes.
\starttext
\dostepwiserecurse{10}{100}{1}
{{\switchtobodyfont[#1pt]#1pt:\definedfont[Serif
(or not at all).
Using MkIV text is slanted fine, independent from font size.
Could anyone confirm the issue?
I can confirm the slant decreases at larger font sizes.
\starttext
\dostepwiserecurse{10}{100}{1}
{{\switchtobodyfont[#1pt]#1pt:\definedfont[Serif*slanted]\vrule\relax
S\vrule\relax lanted
]
\setupfittingpage[offset=1ex]
\starttext
\startTEXpage
a {\em b}
\stopTEXpage
\startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
a {\em b}
\stopTEXpage
\stoptext
Using LMTX higher font size gives less slanted text (or not at all).
Using MkIV text is slanted fine
\startTEXpage
a {\em b}
\stopTEXpage
\startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
a {\em b}
\stopTEXpage
\stoptext
Using LMTX higher font size gives less slanted text (or not at all).
Using MkIV text is slanted fine, independent from font size.
Could anyone confirm the issue?
Many
re not cached in which case every run will
> > > involve parsing the otf / ttf and producing whatever resources needed
> > > (normally cached).
> >
> > interesting. Earlier as the output was showing
> >
> > > mkiv lua stats > loaded patterns: en::1, load t
in which case every run will
involve parsing the otf / ttf and producing whatever resources needed
(normally cached).
interesting. Earlier as the output was showing
mkiv lua stats > loaded patterns: en::1, load time: 0.000
mkiv lua stats > loaded fonts: 4 files: lucidabrightregul
fonts are not cached in which case every run will
> involve parsing the otf / ttf and producing whatever resources needed
> (normally cached).
interesting. Earlier as the output was showing
> mkiv lua stats > loaded patterns: en::1, load time: 0.000
> mkiv lua stats > loaded fo
On 3/31/2023 10:08 PM, Carlos via ntg-context wrote:
sure, why should it, you want lucida so better quit with an error than
kicking in some font; actually cmr math fonts have been obsoleted for way
over a decade by latin modern math fonts in 32 bit font engines
Font loading and processing
;
> It really pays off to buy the official lucida opentype package.
I'll do that eventually.
>
> > mkiv lua stats > loaded fonts: 3 files: lucidanewmathitalic.ttf,
> > lucidanewmathsymbol.ttf, lucidabrightregular.otf
> > mkiv lua stats > font engine: otf 3.133, afm 1.513
On 3/31/2023 1:40 PM, Carlos via ntg-context wrote:
so why not use lucida math fonts?
I have. But only with a couple of math fonts. I don't have all these fonts.
It really pays off to buy the official lucida opentype package.
mkiv lua stats > loaded fonts: 3 fi
On Wed, Mar 29, 2023 at 12:48:53AM +0200, Hans Hagen via ntg-context wrote:
> On 3/28/2023 7:05 PM, Carlos via ntg-context wrote:
> > On Mon, Mar 27, 2023 at 03:43:47PM +0200, Hans Hagen via ntg-context wrote:
> > > On 3/27/2023 3:31 PM, Carlos via ntg-context wrote:
> > &
On 3/28/2023 7:05 PM, Carlos via ntg-context wrote:
On Mon, Mar 27, 2023 at 03:43:47PM +0200, Hans Hagen via ntg-context wrote:
On 3/27/2023 3:31 PM, Carlos via ntg-context wrote:
mkiv lua stats > loaded fonts: 4 files: latinmodern-math.otf,
lmroman10-regular.otf, lucidabrightregular.
On Mon, Mar 27, 2023 at 03:43:47PM +0200, Hans Hagen via ntg-context wrote:
> On 3/27/2023 3:31 PM, Carlos via ntg-context wrote:
>
> > mkiv lua stats > loaded fonts: 4 files: latinmodern-math.otf,
> > lmroman10-regular.otf, lucidabrightregular.ttf, lucidasansregular.t
On 3/27/2023 3:31 PM, Carlos via ntg-context wrote:
mkiv lua stats > loaded fonts: 4 files: latinmodern-math.otf,
lmroman10-regular.otf, lucidabrightregular.ttf, lucidasansregular.ttf
i admit never having seen lucida ttf files (but when opentype ttf files
are used with an afm file pres
nsRegular.ttf filetype=ttf format=ttf
foundname=/usr/local/texlive/2023/texmf-local/fonts/truetype/bandh/lucida/LucidaSansRegular.ttf
fullname=/usr/local/texlive/2023/texmf-local/fonts/truetype/bandh/lucida/LucidaSansRegular.ttf
usedmethod=database
mkiv lua stats > loaded fonts: 4 files: lat
On Sun, Mar 26, 2023 at 01:04:30PM +0200, Henning Hraban Ramm via ntg-context
wrote:
> Am 25.03.23 um 23:42 schrieb Carlos via ntg-context:
>
> > > > fonts | names | 3092 afm files checked, okay
> > > > fonts | names | identifying tree font files with suffix 'AFM'
> > > >
0757f9984eae810b1464/fonts/streams/lucidabrightregularotf-1.tmd'
stripped
Not how I wanted it originally as in Void Linux with texnansi encoding and a
TeXLive2021 prepackaged
mkiv lua stats > loaded fonts: 4 files: lucidabrightregular.otf,
lucidasansregular.otf, latinmodern-math.otf, lmro
On Sun, Mar 26, 2023 at 03:21:35PM +0200, Hans Hagen via ntg-context wrote:
> On 3/26/2023 3:08 PM, Carlos via ntg-context wrote:
> > On Sun, Mar 26, 2023 at 01:04:30PM +0200, Henning Hraban Ramm via
> > ntg-context wrote:
> > > Am 25.03.23 um 23:42 schrieb Carlos via ntg-context:
> > >
> > > >
On 3/26/2023 3:08 PM, Carlos via ntg-context wrote:
On Sun, Mar 26, 2023 at 01:04:30PM +0200, Henning Hraban Ramm via ntg-context
wrote:
Am 25.03.23 um 23:42 schrieb Carlos via ntg-context:
fonts | names | 3092 afm files checked, okay
fonts | names | identifying tree
On Sun, Mar 26, 2023 at 01:04:30PM +0200, Henning Hraban Ramm via ntg-context
wrote:
> Am 25.03.23 um 23:42 schrieb Carlos via ntg-context:
>
> > > > fonts | names | 3092 afm files checked, okay
> > > > fonts | names | identifying tree font files with suffix 'AFM'
> > > >
Am 25.03.23 um 23:42 schrieb Carlos via ntg-context:
fonts | names | 3092 afm files checked, okay
fonts | names | identifying tree font files with suffix 'AFM'
fonts | names | scanning path '/home/ce/.texlive2023/texmf-config'
for AFM files
fonts |
ntg-context wrote:
> > >
> > > >
> > > > ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030: in
> > > > upvalue 'walk_tree'
> > > Maybe your OSFONTDIR is pointing to empty. Does
> >
> > Good call. Thank you for the reminder H
On 3/25/2023 10:36 PM, Carlos via ntg-context wrote:
On Sat, Mar 25, 2023 at 09:45:25PM +0100, Hans Hagen via ntg-context wrote:
On 3/25/2023 8:55 PM, Carlos via ntg-context wrote:
...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030: in
upvalue 'walk_tree'
Maybe your
On Sat, Mar 25, 2023 at 09:45:25PM +0100, Hans Hagen via ntg-context wrote:
> On 3/25/2023 8:55 PM, Carlos via ntg-context wrote:
>
> > ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030:
> > in upvalue 'walk_tree'
> Maybe your OSFONTDIR is pointing
On Sat, Mar 25, 2023 at 09:26:36PM +0100, Hans Hagen via ntg-context wrote:
> On 3/25/2023 8:55 PM, Carlos via ntg-context wrote:
> > Hello list:
> >
> > This is under a fresh TeXLive installation. Sort as to put aside any
> > texlive prepackaged issues.
> >
> > And the followign lines is the
On 3/25/2023 8:55 PM, Carlos via ntg-context wrote:
...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030: in
upvalue 'walk_tree'
Maybe your OSFONTDIR is pointing to empty. Does
mtxrun --script font --reload
work
Hans
On 3/25/2023 8:55 PM, Carlos via ntg-context wrote:
Hello list:
This is under a fresh TeXLive installation. Sort as to put aside any texlive
prepackaged issues.
And the followign lines is the output of the error I've been having with the
call of context on a recent texlive installation by
after.
mtxrun --script cache --erase has also been called out to no avail
registered function call [1160]:
...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.:
Permission denied
stack traceback:
[C]: in upvalue 'func'
...live/2023/texmf-dist/tex/context
On 3/6/23 21:10, Hans Hagen via ntg-context wrote:
> On 3/6/2023 7:46 PM, Pablo Rodriguez via ntg-context wrote:
>> [...]
>> Could anyone confirm that the format file for MkIV (LuaTeX) cannot be
>> generated with current latest (from today [2023.03.06 14:48])?
> hm, loo
On 3/6/2023 7:46 PM, Pablo Rodriguez via ntg-context wrote:
Dear list,
I have the following sample:
\starttext
\null
\stoptext
Trying to compile it with "context --luatex", I get the error message
copied bellow.
Could anyone confirm that the format file for MkIV (LuaT
Dear list,
I have the following sample:
\starttext
\null
\stoptext
Trying to compile it with "context --luatex", I get the error message
copied bellow.
Could anyone confirm that the format file for MkIV (LuaTeX) cannot be
generated with current latest (from today [2023.0
On 12/6/2022 10:04 PM, Rik Kabel via ntg-context wrote:
On 2022-12-06 15:32, Hans Hagen via ntg-context wrote:
On 12/6/2022 9:06 PM, Rik Kabel via ntg-context wrote:
\definelabel[X][text=]
\startTEXpage[offset=1cm]
\X\X[a]\X[b]\X\par
\convertnumber{R}{\ref[number][a]}
On 2022-12-06 15:32, Hans Hagen via ntg-context wrote:
On 12/6/2022 9:06 PM, Rik Kabel via ntg-context wrote:
\definelabel[X][text=]
\startTEXpage[offset=1cm]
\X\X[a]\X[b]\X\par
\convertnumber{R}{\ref[number][a]}
\convertnumber{G}{\ref[number][b]}
\stopTEXpage
maybe like this:
On 12/6/2022 9:06 PM, Rik Kabel via ntg-context wrote:
\definelabel[X][text=]
\startTEXpage[offset=1cm]
\X\X[a]\X[b]\X\par
\convertnumber{R}{\ref[number][a]}
\convertnumber{G}{\ref[number][b]}
\stopTEXpage
maybe like this:
\definelabel[X][text=]
\startTEXpage[offset=1cm]
(\X)
On 2022-01-19 12:39, Rik Kabel via ntg-context wrote:
This is still a problem with the current standalone.
\definelabel[X][text=]
\startTEXpage[offset=1cm]
\X\X[a]\X[b]\X\par
\convertnumber{R}{\ref[number][a]}
\convertnumber{G}{\ref[number][b]}
\stopTEXpage
On 10/26/2022 3:35 PM, Rik Kabel via ntg-context wrote:
On 2022-10-26 07:43, Hans Hagen via ntg-context wrote:
On 10/26/2022 1:52 AM, Rik Kabel via ntg-context wrote:
The following example produces different results when processed by
LMTX and MkIV. In particular, a space between the X and Y
On 2022-10-26 07:43, Hans Hagen via ntg-context wrote:
On 10/26/2022 1:52 AM, Rik Kabel via ntg-context wrote:
The following example produces different results when processed by
LMTX and MkIV. In particular, a space between the X and Y is not
auto-inserted by LMTX, while it is by MkIV
On 10/26/2022 1:52 AM, Rik Kabel via ntg-context wrote:
The following example produces different results when processed by LMTX
and MkIV. In particular, a space between the X and Y is not
auto-inserted by LMTX, while it is by MkIV.
\starttexdefinition TEST #1
#1\autoinsertnextspace
The following example produces different results when processed by LMTX
and MkIV. In particular, a space between the X and Y is not
auto-inserted by LMTX, while it is by MkIV.
\starttexdefinition TEST #1
#1\autoinsertnextspace
\stoptexdefinition
\tt
\starttext
\TEST{X
Adam Reviczky via ntg-context schrieb am 17.09.2022 um 18:14:
Hi,
With the latest upload (2022-09-16 14:41) I wanted to compare some
older projects that I've used with MKIV to the LMTX 2.10.00.
In one of which I am using the Lato 2.0 font
(https://packages.debian.org/sid/fonts-lato
Hi,
With the latest upload (2022-09-16 14:41) I wanted to compare some older
projects that I've used with MKIV to the LMTX 2.10.00.
In one of which I am using the Lato 2.0 font (
https://packages.debian.org/sid/fonts-lato).
With MKIV I get the correct output but LMTX complains about not being
'/usr'
/usr/local/bin/mtxrun:649: cannot open /usr/local/etc/cups/ssl/: Permission
denied
> On 13 May 2022, at 01:57, Gerion Entrup via ntg-context
> wrote:
>
> Hi,
>
> I'm having a problem with TeXLive 2021 in conjunction with MkIV.
> Basically,
Hi,
I'm having a problem with TeXLive 2021 in conjunction with MkIV.
Basically, executing context results in:
% context
mtxrun | unknown script 'context.lua' or 'mtx-context.lua
I researched this and found that probably there is a path problem.
LaTeX seems to be using
context
--luatex --generate"):
system > lua > loading of file
'context/tex/texmf-context/tex/context/base/mkiv/luat-exe.lua' failed:
cannot open
context/tex/texmf-context/tex/context/base/mkiv/luat-exe.lua: No such
file or directory
resolvers > lua > loading
On 4/1/2022 9:19 PM, Denis Maier via ntg-context wrote:
Same here... I haven't managed to run mkiv for months. Not a huge deal, but
anyway.
Best,
Denis
Von: ntg-context im Auftrag von Pablo Rodriguez via
ntg-context
Gesendet: Freitag, 1. April 2022
Same here... I haven't managed to run mkiv for months. Not a huge deal, but
anyway.
Best,
Denis
Von: ntg-context im Auftrag von Pablo Rodriguez
via ntg-context
Gesendet: Freitag, 1. April 2022 20:37:30
An: Hans Hagen via ntg-context
Cc: Pablo Rodriguez
On 4/1/22 18:20, Hans Hagen via ntg-context wrote:
> [...]
> So, today is the day we kind of formally freeze MKIV.
Just a comment on MkIV.
I don’t remember exactly, but I’m afraid that "context --luatex
document" hasn’t been working on my computers (either running Linux or
Win
On 2022-04-01 12:20, Hans Hagen via ntg-context wrote:
Hi,
Normally when we're in the 2022 TeXlive code freeze period, there is a
snapshot release but because there hasn't been that many changes,
maybe a few patches, in MKIV there is no real snapshot this year. But
for the sake
Hi,
Normally when we're in the 2022 TeXlive code freeze period, there is a
snapshot release but because there hasn't been that many changes, maybe
a few patches, in MKIV there is no real snapshot this year. But for the
sake of consistency we can consider today's version that snapshot
en(), orig)
}
\starttext
\stoptext
used to work in ConTeXt mkiv and still works in ConTeXt lmtx, but for
current mkiv versions it breaks with
...mtx/tex/texmf-context/tex/context/base/mkiv/util-zip.lua:610: attempt to
call a nil value (upvalue 'tocardinal1')
stack traceback:
Hi,
The following document
\directlua{
local arch = gzip.compress"I will become much much smaller, once the
overhead is compensated"
local orig = gzip.decompress(arch)
print(arch:len(), orig:len(), orig)
}
\starttext
\stoptext
used to work in ConTeXt mkiv and s
On 1/19/2022 6:29 PM, Rik Kabel wrote:
This is still (or perhaps once again) a problem using the latest MkIV
(context --luatex).
not twice a day upload for something like that -)
Hans
This is still a problem with the current standalone.
\definelabel[X][text=]
\startTEXpage[offset=1cm]
\X\X[a]\X[b]\X\par
\convertnumber{R}{\ref[number][a]}
\convertnumber{G}{\ref[number][b]}
\stopTEXpage
%% The above example fails to compile when there is no tuc
labels \currentlabel :#1
> >> \endcsname \??labels \currentlabel :#1\else \expandafter
> >> \dolabelparentparameter \csname \??labels \currentlabel :\s!parent
> >> \endcsname {#1}\fi \endcsname
> >> \useconstructionstyleandcolor ...pty \else
> >>
csname
\useconstructionstyleandcolor ...pty \else
\dousecurrentstyleparameter \fi \edef \currentcolorparameter
{\labelparameter {#2}
MkIV only, no problem in LMTX.
replace by \c!numbercolor and remake the format
This is still (or perhaps once again) a problem using the latest MkIV
(context --luatex).
\else
\dousecurrentstyleparameter \fi \edef \currentcolorparameter
{\labelparameter {#2}
MkIV only, no problem in LMTX.
replace by \c!numbercolor and remake the format
-
Hans Hagen | PRAG
er {#2}
MkIV only, no problem in LMTX.
--
Rik
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage
away with it.
--
Rik
On 10/27/2021 21:47, Rik Kabel via ntg-context wrote:
Hello list,
The following fails with ConTeXt ver: 2021.10.24 21:45 MKIV but
works with the companion LMTX. The error message is:tex error
> tex error on line 6 in file G:/TestConTeXt/convert.tex: !
Incompati
, Rik Kabel via ntg-context wrote:
Hello list,
The following fails with ConTeXt ver: 2021.10.24 21:45 MKIV but works
with the companion LMTX. The error message is:tex error > tex
error on line 6 in file G:/TestConTeXt/convert.tex: ! Incompatible
glue units , pointing to the sec
,
The following fails with ConTeXt ver: 2021.10.24 21:45 MKIV but works
with the companion LMTX. The error message is:tex error > tex
error on line 6 in file G:/TestConTeXt/convert.tex: ! Incompatible
glue units , pointing to the second \convertnumber line.
\definelabel[XX]%[text=,bef
Hello list,
The following fails with ConTeXt ver: 2021.10.24 21:45 MKIV but works
with the companion LMTX. The error message is:tex error > tex
error on line 6 in file G:/TestConTeXt/convert.tex: ! Incompatible glue
units , pointing to the second \convertnumber line.
\definela
:
On 10/4/2021 12:39 PM, Henning Hraban Ramm via ntg-context wrote:
Hi,
since a while, I can’t run MkIV any more, even after several runs of install.sh
(and mtxrun --generate, of course).
It’s the same on my Mac and my Linux laptop (of course the bin dir is different
on the latter):
$ context
version: 2021.09.26 17:00
Greetings
Marcus Vinicius
On Mon, Oct 4, 2021 at 8:55 AM Henning Hraban Ramm via ntg-context
wrote:
Am 04.10.2021 um 13:06 schrieb Hans Hagen :
On 10/4/2021 12:39 PM, Henning Hraban Ramm via ntg-context wrote:
Hi,
since a while, I can’t run MkIV any more, even
” directory (around August 20).
> Previously, the cache for LMTX still used files under luatex-cache, just
> like MKIV. But since that change, the “context -—generate” call no longer
> updates files in luatex-cache, only in luametatex-cache.
>
>
> That is not a big problem unless som
Hi,
Here is what I assume has happened:
Hans gave LMTX its own "luametatex-cache” directory (around August 20).
Previously, the cache for LMTX still used files under luatex-cache, just like
MKIV. But since that change, the “context -—generate” call no longer updates
files in luatex-
> Am 04.10.2021 um 15:33 schrieb Taco Hoekwater via ntg-context
> :
>
> We are busy with this off-list.
>
> If it is urgent:
>
> luatex --luaonly ~/lmtx/tex/texmf-osx-64/bin/mtxrun.lua --generate
>
> fixed it for me (you’ll need to adjust the path, of course)
For me too, while it didn’t
0/4/2021 12:39 PM, Henning Hraban Ramm via ntg-context wrote:
> >> Hi,
> >> since a while, I can’t run MkIV any more, even after several runs of
> >> install.sh (and mtxrun --generate, of course).
> >> It’s the same on my Mac and my Linux laptop (of cours
21 12:39 PM, Henning Hraban Ramm via ntg-context wrote:
> >> Hi,
> >> since a while, I can’t run MkIV any more, even after several runs of
> install.sh (and mtxrun --generate, of course).
> >> It’s the same on my Mac and my Linux laptop (of course the bin dir is
>
> Am 04.10.2021 um 13:06 schrieb Hans Hagen :
>
> On 10/4/2021 12:39 PM, Henning Hraban Ramm via ntg-context wrote:
>> Hi,
>> since a while, I can’t run MkIV any more, even after several runs of
>> install.sh (and mtxrun --generate, of course).
>> It’s the s
> Am 04.10.2021 um 13:20 schrieb Taco Hoekwater :
>
>> On 4 Oct 2021, at 12:39, Henning Hraban Ramm via ntg-context
>> wrote:
>>
>> I thought that was related to the server/provider move, but I guess it isn’t.
>>
>> It’s a bit annoying that install.sh leaves ~/lmtx/bin in the PATH, so that a
> On 4 Oct 2021, at 12:39, Henning Hraban Ramm via ntg-context
> wrote:
>
> I thought that was related to the server/provider move, but I guess it isn’t.
>
> It’s a bit annoying that install.sh leaves ~/lmtx/bin in the PATH, so that a
> call to mtxrun can’t find any configuration.
That is
On 10/4/2021 12:39 PM, Henning Hraban Ramm via ntg-context wrote:
Hi,
since a while, I can’t run MkIV any more, even after several runs of install.sh
(and mtxrun --generate, of course).
It’s the same on my Mac and my Linux laptop (of course the bin dir is different
on the latter):
$ context
Hi,
since a while, I can’t run MkIV any more, even after several runs of install.sh
(and mtxrun --generate, of course).
It’s the same on my Mac and my Linux laptop (of course the bin dir is different
on the latter):
$ context --version
mtx-context | ConTeXt Process Management 1.04
mtx
ext
8< --
I see a difference in MkIV and LMTX work:
- MkIV always put a blank line despite '\blank[overlay]' command;
- with \blank[overlay] and 'intext' option LMTX clutters item label (number in
this case).
Q1: is this the expected be
Hi,
After https://mailman.ntg.nl/pipermail/ntg-context/2021/102052.html
It seems that there is no backward compatibility between MkIV and LMTX
for textext.dflt (MVE below)
| MkIV | LMTX |
-|---|--|
textext.dflt | OK | KO | as DefauLT (unlike ulft
Aditya Mahajan via ntg-context writes:
> On Mon, 30 Aug 2021, Rainer J.H. Brandt via ntg-context wrote:
>
> > But, as I said, my texmf.cnf sets TEXMFCACHE to $TEXMFSYSVAR;$TEXMFVAR,
> > and TEXMFSYSVAR is /var/opt/texlive. Why is that ignored?
>
> mtxrun (and context MK
Arthur Rosendahl writes:
> On Mon, Aug 30, 2021 at 12:48:05PM +0200, Rainer J.H. Brandt via ntg-context
> wrote:
> > But, as I said, my texmf.cnf sets TEXMFCACHE to $TEXMFSYSVAR;$TEXMFVAR,
> > and TEXMFSYSVAR is /var/opt/texlive. Why is that ignored?
>
> Do you have write permission on that
On Mon, Aug 30, 2021 at 12:48 PM Rainer J.H. Brandt via ntg-context <
ntg-context@ntg.nl> wrote:
> luigi scarso via ntg-context writes:
> > > > On Fri, Aug 27, 2021 at 10:35 AM Rainer J.H. Brandt via ntg-context <
> > > > ntg-context@ntg.nl> wrote:
> > > > > The TeXlive documentation says that
On Mon, 30 Aug 2021, Rainer J.H. Brandt via ntg-context wrote:
> But, as I said, my texmf.cnf sets TEXMFCACHE to $TEXMFSYSVAR;$TEXMFVAR,
> and TEXMFSYSVAR is /var/opt/texlive. Why is that ignored?
mtxrun (and context MKIV and LMTX) do not read texmf.cnf rather read values
from contextc
On Mon, Aug 30, 2021 at 12:48:05PM +0200, Rainer J.H. Brandt via ntg-context
wrote:
> But, as I said, my texmf.cnf sets TEXMFCACHE to $TEXMFSYSVAR;$TEXMFVAR,
> and TEXMFSYSVAR is /var/opt/texlive. Why is that ignored?
Do you have write permission on that directory?
Arthur
luigi scarso via ntg-context writes:
> > > On Fri, Aug 27, 2021 at 10:35 AM Rainer J.H. Brandt via ntg-context <
> > > ntg-context@ntg.nl> wrote:
> > > > The TeXlive documentation says that ConTeXt uses TEXMFCACHE,
> > > > which uses the default $TEXMFSYSVAR;$TEXMFVAR in my texmf.cnf.
> > > > My
On Mon, Aug 30, 2021 at 11:49 AM Rainer J.H. Brandt via ntg-context <
ntg-context@ntg.nl> wrote:
> Hello Luigi,
>
> you asked:
> > On Fri, Aug 27, 2021 at 10:35 AM Rainer J.H. Brandt via ntg-context <
> > ntg-context@ntg.nl> wrote:
> >
> > > Dear
Hello Luigi,
you asked:
> On Fri, Aug 27, 2021 at 10:35 AM Rainer J.H. Brandt via ntg-context <
> ntg-context@ntg.nl> wrote:
>
> > Dear experts,
> >
> > I want to use ConTeXt MkIV as supplied by TeXlive 2021.
> > After installation, I ran "mtxrun --gen
On Fri, Aug 27, 2021 at 10:35 AM Rainer J.H. Brandt via ntg-context <
ntg-context@ntg.nl> wrote:
> Dear experts,
>
> I want to use ConTeXt MkIV as supplied by TeXlive 2021.
> After installation, I ran "mtxrun --generate".
> I also tried "context --generate
Dear experts,
I want to use ConTeXt MkIV as supplied by TeXlive 2021.
After installation, I ran "mtxrun --generate".
I also tried "context --generate".
Both create output in the wrong place.
The TeXlive documentation says that ConTeXt uses TEXMFCACHE,
which uses the
On 8/25/2021 6:05 PM, Adam Reviczky via ntg-context wrote:
Hi,
I have been using the ansi and ansilog flags in the past and they work
fine with lmtx, but do not seem to make a difference with luatex/mkiv.
(There was a thread back in 2019:
https://mailman.ntg.nl/pipermail/ntg-context/2019
Hi,
I have been using the ansi and ansilog flags in the past and they work fine
with lmtx, but do not seem to make a difference with luatex/mkiv. (There
was a thread back in 2019:
https://mailman.ntg.nl/pipermail/ntg-context/2019/095666.html)
I am trying just a simple hello world:
\starttext
On 6/5/21 4:07 PM, Hans Hagen wrote:
> On 6/5/2021 11:08 AM, Pablo Rodriguez wrote:
>> [...]
>> Could anyone confirm the issue?
>
> a side effect of more detail in final node lists (that make up the lines)
>
>> Many thanks for your help,
> fixed in next upload
Hans, many thanks for the fix.
the output I get (MkIV and LMTX).
Could anyone confirm the issue?
a side effect of more detail in final node lists (that make up the lines)
Many thanks for your help,
fixed in next upload
Hans
{a.b\\/c.d\letterhash e}
\stopitemize
\stopTEXpage
\stoptext
I’m using current latest from 2021.06.04 17:28.
LuaTeX generates the link rectangle right.
LuaMetaTeX generates a wrong link rectangle.
In the attached image, you can see the output I get (MkIV and LMTX).
Could anyone confirm
\usemodule[newmml]
> > \starttext
> > \xmlprocessdata{}{
> >
> >E
> >
> > π
> >
> >
> > }{}
> > \stoptext
> >
> > The π symbol does not show in red.
> Kind of trivial ... i'll send you a patched module.
and see where we need to add
it. I'll then adapt the mkiv file before taking a look at upgrading the
lmtx one.
For decades this mathml stuff has been a bit of a pain, because when one
uses it for a mixed web / text project one always needs to satisfy the
latest greatest either or not bugged web
Apologies Hans.
MWE:
\usemodule[newmml]
\starttext
\xmlprocessdata{}{
E
π
}{}
\stoptext
The π symbol does not show in red.
Duncan
On Thu, 27 May 2021 at 17:18, Hans Hagen wrote:
> On 5/27/2021 5:47 PM, Duncan Hothersall wrote:
> > Hello list.
> >
> > I'm trying to use
On 5/27/2021 5:47 PM, Duncan Hothersall wrote:
Hello list.
I'm trying to use colour in some MathML formulae using the mathcolor
attribute. It seems to have no effect on the output. I can
see \applymmlmathcolor in the x-mathml.mkiv source but I can't see how
to make it work. Does anyone have
1 - 100 of 3484 matches
Mail list logo
